chore(release): Upgrade self-hosted Weaviate to 1.38 and weaviate-client to 4.22#38214
Draft
dudanogueira wants to merge 2 commits into
Draft
chore(release): Upgrade self-hosted Weaviate to 1.38 and weaviate-client to 4.22#38214dudanogueira wants to merge 2 commits into
dudanogueira wants to merge 2 commits into
Conversation
- Bump image to cr.weaviate.io/semitechnologies/weaviate:1.38.1 across docker-compose.yaml, docker-compose.middleware.yaml, and the template - Bump weaviate-client 4.20.5 -> 4.22.0 (vdb-weaviate package + uv.lock) - Add missing WEAVIATE_GRPC_ENDPOINT / EXPOSE_WEAVIATE_GRPC_PORT entries to api/.env.example, integration test env, and middleware.env.example
dudanogueira
requested review from
QuantumGhost,
crazywoola and
laipz8200
as code owners
dosubot
Bot
added
size:XS
5 tasks
41tair
changed the title
Member
|
Hi, thanks for your contribution! Would you like to add some migration docs to docs ? Since this upgrade spans multiple versions, I think having a migration guide is necessary. |
Author
|
hi there! Sure thing. I will still run some tests, but I do not expect and breaking change. We advise to no jump versions. For 1.27 -> 1.27.latest -> 1.28.latest -> etc etc I will mark it as draft while I work on those tests. Also, I am working on exposing some other options, such as compression, different index options and multi tenant support. This can help reducing resource consumption and large scale scenarios. Also, an integration for memory with our recently launched memory layer. Thanks! |
Register the X-Weaviate-Client-Integration header (value: dify/<version>) on the Weaviate client so the server can attribute traffic to Dify in its telemetry, alongside the built-in X-Weaviate-Client header. This mirrors the approach used by other official Weaviate integrations. The version is resolved from dify_config.project.version, falling back to the dify-api package metadata and then "unknown". Registration is best-effort and wrapped in try/except so it never breaks client initialization on older weaviate-client releases that lack the integrations API.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Upgrades the bundled self-hosted Weaviate from
1.27.0to 1.38.1 and theweaviate-clientdependency from4.20.5to 4.22.0. Pure version bump + env-example consistency; no behavior change to the VDB code path.cr.weaviate.io/semitechnologies/weaviate:1.38.1indocker/docker-compose.yaml,docker/docker-compose.middleware.yaml, anddocker/docker-compose-template.yaml.weaviate-client4.20.5 → 4.22.0inapi/providers/vdb/vdb-weaviate/pyproject.toml(+uv.lock).WEAVIATE_GRPC_ENDPOINT/EXPOSE_WEAVIATE_GRPC_PORTentries toapi/.env.example, the integration-test env, andmiddleware.env.example.Fixes #38211
Screenshots
Checklist
make lint && make type-check(backend) — both pass. Frontendpnpm exec vp stagedN/A (no frontend changes).From Claude Code